-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support of private frontier Key for workflow-specific caching #33505
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33505/22243
|
A new Pull Request was created by @ggovi for master. It involves the following packages: CondCore/DBOutputService @malbouis, @yuanchao, @christopheralanwest, @cmsbuild, @tlampen, @ggovi, @pohsun, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4da35a/14481/summary.html Comparison SummarySummary:
|
+1 |
+alca |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
We are enabling the use of workflow-specific private keys for the condition data access with frontier. The goal is ensuring that the fresh-keys identifying the cached data in the squids are not shared with other workflows/processes. In this way, unintended interferences and unwanted data are avoided.
The keys will be provided as an external parameter for the read-only ESSource-based workflows, and as the content of a specified file for the update-capable workflows.
PR validation:
Unit tests and integration tests